The reliable way to assign a Knight is to read the whole Quest, cover every important stat, account for known and hidden traits, repair for the displayed damage, and preserve enough roster capacity for approaching deadlines. A high total alone does not guarantee the desired result, especially when a character-specific outcome replaces the normal resolution.
Reading Knight Stats
The six reported stats are Strength, Agility, Charisma, Magic, Wits, and Luck. Detailed community research describes a 0-to-15 scale and says each Quest can test one or more of those values. Use the current character sheet and Quest card because levels and equipment can make a static roster listing obsolete in your timeline.
Cover the complete requirement set rather than selecting the Knight with the single highest number. A party that excels physically but misses a social or magical check may still underperform, and adding another poorly matched Knight can consume availability without solving the gap. The supplied research contains proposed scoring details, but the exact hidden formula is not reproduced here.
Armour and stats answer different questions. Stats contribute to suitability, while armour helps a Knight survive the damage range shown for the assignment. Repair around the actual risk, then use equipment to address a known weakness or useful condition instead of buying upgrades without a planned job.
Visible and Hidden Traits
Known attributes appear in the glossary when a Knight joins. Hidden attributes are reported to function before discovery, which is why a seemingly correct party can produce an unexpected result. Conversations, investigations, story events, and Quest debriefs gradually explain those differences.
Some traits modify broad situations, while others act as keys for a special outcome. Angelica's animal connection, Alwena's short-duration restriction, Ursula's unusual relationship with death, and Chester's unpredictable stat behavior illustrate very different kinds of rule. Read the trait wording and the Quest conditions together rather than treating every attribute as a flat bonus.
Alwena is also reported to reveal a subset of hidden rumors one at a time. Her own recruitment timing is disputed, but the investigation function makes her valuable when a new Knight has failed for no visible reason. Prioritize information before a route-defining Quest, then record what the result confirms.
Matching Knights to Quests
Start with deadline and duration. A perfect specialist who returns after the story deadline is not a valid solution, and sending every flexible Knight away can leave the next emergency uncovered. Reserve capacity first, then compare requested party size, stats, conditions, damage, and rewards.
Next, separate mechanical fit from preference. Supplied guides report that liked and disliked Quest types primarily affect affinity rather than ordinary Quest score. A Knight may therefore be capable but unhappy, or enthusiastic but statistically unsafe, and the correct choice depends on whether the reign can absorb relationship loss or assignment failure.
Unexpected Outcomes require another decision: do you want the special result? Angelica may handle an animal problem in a way that differs from the ordinary hunt, and a character-specific branch can replace normal rewards. The debrief is part of the assignment process because it reveals whether the party matched the result you intended, not merely whether the screen used the word success.
Finally, keep the source of every recommendation visible. Community lists include exact thresholds from individual runs, but a fixed 92-Quest assignment table and proposed score formula are not necessary for good play. Trust requirements displayed in the current build and label unreplicated special conditions To be confirmed.
Meals and Affinity
Favorite meals are reported to improve affinity and provide a small temporary Quest benefit. The detailed source lists Galette-Saucisse, Croque-Monsieur, Prefou, Crepe, Brizhian Butter Shortbread, and Lion's Taco as the six dishes. Use the preference revealed in your own glossary because the useful decision is who needs relationship support before the next assignment.
Affinity also changes through preferred or disliked work, personal conversations, and reactions to the Sovereign's style. A Knight who repeatedly receives unwanted assignments may eventually leave even if every Quest succeeds. Rotate difficult work, use meals deliberately, and invest in conversations with specialists you need for a long route.
Food does not repair a bad party. Serve it after selecting a team that covers the Quest and can survive the damage, not before. Its best role is to strengthen an already reasonable assignment while protecting loyalty.
Roster Planning by Act
The supplied roster guide reports six seats in Act 1, eight in Act 2, and ten in Act 3 for a cast of 24. Early regional forks make The Wolf conflict with Silgur and Brunhilda conflict with Tarcus in the documented routes. Reserve seats for the branch you want instead of recruiting every early candidate simply because the audience is available.
Act 2 planning should account for conditional candidates such as Alwena, Ligia, Childeric, Zolta, Oliver, and Daguez. Several need an empty seat at a specific audience, while others depend on opening decisions, low faction satisfaction, tournament results, or a regional chain. Alwena's earliest Act and Zolta's valid cheating party disagree across sources, so those details are To be confirmed.
Later candidates can add strong or specialized coverage, but they cannot undo a full table. List the stat gaps and Quest conditions your current team handles poorly, then recruit for those needs and the character stories you intend to follow. Rewind can restore a missed branch, but it also erases later roster development and equipment.
King Slayer Preparation Report
One supplied source documents a single Act 2 run after the King Slayer gives a five-cycle warning. The player stopped opening long optional routes, brought core Knights home, protected specialized equipment, and waited to compare the final resolution options before repairing the party. This is a single-run report, not a complete test of every encounter state.
In that run, the chosen purification route required four Knights and displayed 2–5 Damage Risk. The successful party was reported as Rufus, Gideon, Arron, and Ursula, and another visible route reportedly required all six available Knights. Universal applicability of that party, party size, route availability, and damage range is To be confirmed.
The practical lesson is valid without assuming the numbers are fixed. Treat the warning as a scheduling deadline, finish only near-complete permanent rewards, leave room for overlapping emergencies, and wait for the actual resolution screen before redistributing equipment. Repair for the maximum damage shown in your game and build around the route you actually select.
Conflicts and Caveats
Community sources agree on the broad management systems but conflict on recruitment details and identity branches. Rufus is described both as The Wolf transformed and as a recruit with multiple routes; Chester's goose clues vary; Alwena is labeled both unrestricted and Act 2 or later. Each unresolved universal claim is To be confirmed.
The detailed Knight reference also proposes exact affinity values, Quest-score thresholds, and hidden calculations. Those numbers are omitted because the task research does not independently establish the formula across versions and routes. Use them, if encountered elsewhere, as hypotheses to compare with the current result screen rather than guaranteed mechanics.